Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/`@ant/claude-for-chrome-mcp/src/bridgeClient.ts:
- Around line 567-574: The log and telemetry currently include the full
user-specific WebSocket URL (wsUrl) and potentially raw bridge messages; update
the code around wsUrl construction and usage (references: wsUrl,
bridgeConfig.url, serverName, logger.info, trackEvent) to redact sensitive
components before logging or tracking by replacing or removing the userId and
any query/path fragments, and ensure trackEvent only sends a minimal allowlist
of safe fields (e.g., host/origin and connection status) rather than the full
URL or raw message payloads; apply the same redaction when logging in the
connection/handshake code paths (also at the other affected site around the code
referenced at lines 617-619).
- Around line 529-564: Awaiting bridgeConfig.getUserId() and
bridgeConfig.getOAuthToken() is unprotected so if either rejects connect()
leaves this.connecting true; wrap each await (or the whole credential-fetch
block in connect()) in a try/catch, and in the catch set this.connecting =
false, compute durationMs using this.connectionStartTime, logger.error with the
caught error, call trackEvent with an appropriate error_type (e.g.,
"credential_lookup_error"), invoke this.context.onAuthenticationError?.(), and
then return/exit so reconnect attempts and ensureConnected() aren’t blocked.
- Around line 626-660: The close/error handlers for this.ws (inside the
ws.on("close", ...) and ws.on("error", ...) blocks) currently schedule
reconnection but leave this.pendingCalls unresolved, causing callers to hang;
add logic to immediately fail and clear all in-flight calls when the socket
drops by iterating this.pendingCalls (or similar pending call store), invoking
each stored reject/callback with a descriptive Error (e.g. "bridge disconnected"
or include code/message), removing entries from the map, and then proceed to set
connected/authenticated flags and call this.scheduleReconnect(); alternatively
extract this into a helper like failPendingCalls(reason) and call it from both
the close and error handlers.
- Around line 452-471: Before calling queryBridgeExtensions(), first check the
WebSocket connection state (this.ws and this.ws.readyState === WebSocket.OPEN)
and return null immediately if the socket is not open; move the existing
readiness check (this.ws?.readyState !== WebSocket.OPEN) to precede the
queryBridgeExtensions() call in the method that uses
selectedDeviceId/previousSelectedDeviceId/pendingPairingRequestId so you don't
wait DISCOVERY_TIMEOUT_MS and mistakenly return "no_other_browsers".

In `@packages/`@ant/claude-for-chrome-mcp/src/mcpSocketClient.ts:
- Around line 144-149: The logger calls in the isToolResponse branch and the
final else currently interpolate the message object into a template literal
(producing “[object Object]”); change those logger.info calls to either pass the
object as a separate argument (e.g. logger.info(`[${serverName}] Received tool
response:`, message) and logger.info(`[${serverName}] Received unknown
message:`, message)) or stringify the object (e.g. JSON.stringify(message)) so
the actual message content is logged; update the two spots around
isToolResponse, logger.info and the final else to use one of these approaches
and leave handleResponse(message) unchanged.

---

Nitpick comments:
In `@docs/features/claude-in-chrome-mcp.md`:
- Around line 16-51: Add a language specifier (e.g., text or plaintext) to the
fenced code blocks that contain the ASCII flow diagram and the directory listing
shown in the diff (the block starting with "CLI 启动" and the block showing
"packages/@ant/claude-for-chrome-mcp/src/"); update those triple-backtick fences
to ```text so static analysis no longer flags them as missing language
identifiers.

In `@packages/`@ant/claude-for-chrome-mcp/src/bridgeClient.ts:
- Around line 8-17: Replace the relative imports that pull in
SocketConnectionError and the type symbols from "./mcpSocketClient.js" and
"./types.js" with the configured src/ path alias imports (e.g. import {
SocketConnectionError } from "src/mcpSocketClient" and import {
localPlatformLabel, type BridgePermissionRequest, type ChromeExtensionInfo, type
ClaudeForChromeContext, type PermissionMode, type PermissionOverrides, type
SocketClient } from "src/types"), preserving the exact imported identifiers;
update any file extension usage to match the project's tsconfig path mapping so
TypeScript resolves the aliased modules.

In `@packages/`@ant/claude-for-chrome-mcp/src/mcpSocketClient.ts:
- Around line 249-285: ensureConnected() starts polling after calling connect(),
but if connect() throws (e.g., security validation failure) the polling loop
keeps running until the timeout and the original error is lost; change
ensureConnected() to catch errors from this.connect() and record the failure
(e.g., set a new property like this.lastConnectError or this.connectError), then
have the polling routine (in ensureConnected) check that property and
immediately reject with that stored error (and clear timers) instead of waiting
for the 5s timeout; reference ensureConnected, connect, this.connected,
this.connecting and add a short-lived error flag/property to propagate connect()
failures quickly.

In `@packages/`@ant/claude-for-chrome-mcp/src/toolCalls.ts:
- Around line 85-98: Add defensive runtime validation for the tool call response
before asserting its shape: after the socketClient.callTool(...) call, verify
response is a non-null object and that at least one of response.result or
response.error exists and is an object or string; if validation fails, return
the existing fallback ({ content: [{ type: "text", text: "Tool execution
completed" }] }). Then safely destructure into result and error (used by
contentData and isError) knowing the shape is valid. Ensure validations
reference the existing symbols response, result, error, contentData, and isError
so the fallback behavior stays identical when the response is malformed.